Write down the route a landed record's stale evidence takes, and point two checklist links at the file that holds them - #219

Two document-only changes on one branch. Both land text and nothing else, so
they share a pull request rather than moving the mainline under each other for
no reason. They are separate commits and separate topics.

#218, the two links that resolve to nothing

docs/promotion.md wrote both of its decision-record links relative to the
repository root rather than to the file that holds them, so each resolved to a
path under docs/docs/ and neither opened. The label keeps the full path and
the target is now relative to docs/, which is how the nine links in
docs/operator-guide.md and docs/privacy.md are written.

The done-condition asks that grep -rn '](docs/' docs/ --include=*.md return
nothing. At 36eddf59e199659baa2cf6a6eec2731da697a338:

grep -rn '](docs/' docs/ --include=*.md
exit=1

And every link in that file resolves from the directory that holds it:

grep -oE '\]\([^)#][^)]*\)' docs/promotion.md | sed 's/^](//; s/)$//' |
  while read -r l; do (cd docs && test -e "$l" && echo "ok   $l" || echo "MISS $l"); done
ok   decisions/0005-how-a-result-leaves.md
ok   ../LICENSE
ok   decisions/0018-the-licence-of-this-board.md
ok   decisions/0020-consent-to-promote-under-other-terms.md
ok   decisions/0013-how-the-record-format-changes.md

#216, the route a landed record's stale evidence takes

What was left of that issue was the route by which a landed record carrying
evidence that no longer reproduces is repaired, written down, and both sites
left in whatever state the route says. The route was decided on the issue and
lived only there, so this adds
docs/decisions/0026-evidence-in-a-landed-record-that-stopped-reproducing.md:
a landed record's evidence is never brought up to date, because a paste is a
measurement of its date rather than a claim about today. Where the decision
still stands on today's evidence, nothing happens. Where the premise fell, the
answer is a successor record carrying the fresh measurement, never an edit.

Records 0012 and 0018 are read against that test in the record's second
section, and both stand on today's evidence, so neither is edited and neither
gains a successor. 0012 makes itself superseded only if entry four of issue
#46 answered source only, and record 0021 decides that this board publishes
signed downloadable artefacts, so that conditional cannot fire. 0018 decides
GPL-3.0 and the three readings it said disagreed now agree with it.

Every paste in the new record was reproduced before it was written, at
55ef1616e1da8889c005fb7f185fae613557e839:

gh issue view 46 --repo Flowfin/lab --json state --jq '.state'
CLOSED
gh api repos/Flowfin/lab --jq '.license.spdx_id'
GPL-3.0
gh issue view 47 --repo Flowfin/lab --json state --jq '.state'
CLOSED
git grep -n 'const DeclaredLicence' origin/main -- internal/invariants/invariants.go
origin/main:internal/invariants/invariants.go:92:const DeclaredLicence = "GNU GENERAL PUBLIC LICENSE"

One clause of that issue's original done-condition is deliberately not met, and
it is the clause the route overturned. It asks that git grep -n 'issue #46'
return no site asserting an entry is open, and one site still does:

git grep -n 'issue #46' -- . | cut -d: -f1,2
docs/decisions/0001-the-runner-is-written-in-go.md:70
docs/decisions/0005-how-a-result-leaves.md:53
docs/decisions/0012-the-supported-platforms.md:78
docs/quality-parity.md:654

The first two are each about their own record's scope and the issue body puts
them outside its scope; the fourth says the entry is answered. The third is the
one, and under the route above it stays. That clause was written before the
route existed, and the issue's own later statement of what is left replaces it:
the route is decided and written down, and both sites are left in whatever
state the route says.

The means

A decision record in docs/decisions/, because this is a rule later work
depends on and CONTRIBUTING.md sends such a rule there. Nothing else in this
tree holds one, record 0000 already fixes the shape it has to take, and the
existing checks read that directory, so the artefact is judged by the suites
that already exist rather than by a parallel apparatus.

What I ran

go build ./cmd/... ./internal/...
go vet ./cmd/... ./internal/...
gofmt -l cmd internal
go run ./cmd/lab check .
go test -count=1 ./cmd/... ./internal/...

gofmt -l printed nothing. The checker printed:

examined .
1 experiment directory walked, 1 record read
27 decision records read
0 refused

Every package in the suite reported ok.

What this does not carry

No second reader tonight. Nobody but me has read these two commits, and the
evidence above stands in place of that reading rather than alongside it. Both
changes are text: one moves four link characters, the other adds a file that
nothing imports and no run executes.

Nothing here re-scores the board and neither change claims a re-score. The
record's own second section is a reading taken on 2026-08-29 and is subject to
the rule the record states about pastes.

Closes #216
Closes #218